feat: include provider type in schema (#34)#35
Conversation
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 57 minutes and 55 seconds. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Pull request overview
Adds database provider information to the schema metadata endpoint so clients (e.g., tooling/UI) can infer the underlying datasource type.
Changes:
- Extend
GET /api/schemaresponse to includeprovider.typefrom the parsed ZModel datasource config. - Bump package version from
0.4.1to0.4.2.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| src/server.ts | Adds provider.type to the /api/schema JSON response payload. |
| package.json | Version bump to publish the new schema metadata output. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
No description provided.